Skip to content

Conversation

@DhruvBhatheja
Copy link
Contributor

@DhruvBhatheja DhruvBhatheja commented Oct 2, 2025

PR Description:

Pull Request Checklist

Overview

  • I have read and understood the CONTRIBUTING.md guidelines
  • My pull request has a descriptive title that accurately reflects the changes
  • I've included only files relevant to the changes described in the PR title and description
  • I've created a new branch in my forked repository for this contribution

Code Quality

  • My code is relevant to ServiceNow developers
  • My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
  • I've disclosed use of ES2021 features (if applicable)
  • I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

  • I've placed my code snippet(s) in one of the required top-level categories:
    • Core ServiceNow APIs/
    • Server-Side Components/
    • Client-Side Components/
    • Modern Development/
    • Integration/
    • Specialized Areas/
  • I've used appropriate sub-categories within the top-level categories
  • Each code snippet has its own folder with a descriptive name

Documentation

  • I've included a README.md file for each code snippet
  • The README.md includes:
    • Description of the code snippet functionality
    • Usage instructions or examples
    • Any prerequisites or dependencies
    • (Optional) Screenshots or diagrams if helpful

Restrictions

  • My PR does not include XML exports of ServiceNow records
  • My PR does not contain sensitive information (passwords, API keys, tokens)
  • My PR does not include changes that fall outside the described scope

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your submission. It appears that this pull request contains more files than described in the title. Please review and update the pull request to either remove the extra/unintended files or to update the description to be more comprehensive. Ensure your contributions are meaningful and adhere to the project’s standards. You can create a new branch on your forked repository to avoid accidental inclusions of new commits in the future. Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one.

@Atul-LNG
Copy link
Contributor

Atul-LNG commented Oct 2, 2025

Hi @DhruvBhatheja
Thanks for taking action. However, I still see that 4 files have been changed.
You’ll need to fork the repo again, include only the 2 required files, and resubmit the PR.

Ideally, this PR should contain changes to only 2 files, but currently, it's showing 4.

Screenshot 2025-10-02 at 11 15 00

@Atul-LNG
Copy link
Contributor

Atul-LNG commented Oct 2, 2025

Hi @DhruvBhatheja
I am closing this PR for now without merging. Please take the necessary steps , remove any unnecessary files

Don’t get discouraged — we’re all learning. Take your time and come back with only the required files.

@Atul-LNG Atul-LNG closed this Oct 2, 2025
@DhruvBhatheja DhruvBhatheja deleted the Case-Base64-Encode-Before-Save-/-Decode-on-Display branch October 3, 2025 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants